System and method for capture and distribution of information collected from signs

ABSTRACT

Disclosed is a method and apparatus for capturing, collecting, and distributing event information displayed on signs. The method may include capturing, by a mobile device, an image of a sign that displays information for an event. The method may also include extracting information for the event from the captured image of the sign, and determining a location of the mobile device when the image of the sign was captured. Furthermore, the method may include uploading, to a server, a time when the image was captured, the information for the event extracted from the captured image, a location of the event determined from extracted event information, a location of the sign, or a combination thereof.

FIELD

The subject matter disclosed herein relates generally to the capture anddistribution of event information displayed on ephemeral andnon-ephemeral signs.

BACKGROUND

Social networking systems, microblogging systems, bulletin boardsystems, etc. have developed as important sources for distributinginformation. These systems, which require user generation of content,are not adept at distributing information for locally advertised events,such as event advertisements listed on signs (e.g., signboards, sandwichboards, fliers, posters, etc.) at real world locations and for which thesubject event or advertisement may only be ongoing for a limited timeperiod. For example, a signboard placed on a street corner may displayinformation relating to a real estate listing at a specific address fora specific date and time, a yard sale poster may be placed at astoplight and simply have a graphic that points down a street with thewords “Yard Sale”, a sign held by a person may advertise a sale at anearby store by listing the name of the store and pointing at the storeslocation, as well as other advertisements for local and limited timeevents.

The above described example signs are typically ephemeral, in that theyare placed and removed from their real world locations after a couple ofhours, a day, or some other time period. Furthermore, there may be noother record of the event for which the signs advertise, except throughthe sign's own content. When there is a record of the event advertisedby the sign, such as a real estate open house corresponding to a sign, auser would be required to manually search through web pages, real estatelistings, real estate agent company listings, etc., enter query data,and otherwise search for the advertised listing's details. Such actionsdistract users from their current task at hand, such as driving, whichmay potentially be very dangerous. In addition to the safetyconsiderations with distributing the advertised event's details,potentially interested parties may not even know of an advertised eventunless they are proximate to and physically view the sign. Furthermore,even if there were a way to distribute information concerning the event,sign-based event advertisements are often incomplete regardingsignificant event details. For example, a sign may fail to display anevent's address, a duration of the event, whether an event is stilloccurring, etc.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an exemplary system architecture forcapturing, collecting, and distributing event information displayed onsigns;

FIG. 2 is block diagram of one embodiment of a system including a motorvehicle and an event aggregation server;

FIG. 3 is a flow diagram of one embodiment of a method for capturing,collecting, and distributing event information; and

FIG. 4 is a flow diagram of one embodiment of a method for capturing,collecting, and distributing event information with a mobile device andan event aggregation server.

DETAILED DESCRIPTION

The word “exemplary” or “example” is used herein to mean “serving as anexample, instance, or illustration.” Any aspect or embodiment describedherein as “exemplary” or as an “example” in not necessarily to beconstrued as preferred or advantageous over other aspects orembodiments.

FIG. 1 is a block diagram of an exemplary system architecture 100 forcapturing, collecting, and distributing event information displayed onsigns. In one embodiment, a motor vehicle 110 includes an imaging system112 (e.g., one or more cameras, RADAR, LIDAR, image analysis processor,etc.) and a positioning system 114 (e.g., GNSS system, such as a globalpositioning system (GPS)). In embodiments, the imaging system 112 andpositioning system 114 may be used by motor vehicle 110 to performautonomous driving, semi-autonomous driving, or other driver assistancefunctions. Motor vehicle 110 utilizes imaging system 112 to capture animage of an event advertisement sign 150, such as a sign, poster,signboard, sandwich board, etc. placed on a street corner, attached to atraffic light, held by a person, etc. For example, sign 150 illustratesa real estate advertisement signboard typically placed on a streetcorner with event information providing the purpose of the sign (e.g., alisting for real estate), the listing agent (e.g., Jane Doe), an addressassociated with a listed property (e.g., 1234 April Boulevard), and adirectional indicator relative to the sign's 150 real world location.Other signs with more or less information concerning an advertisedevent, may also be captured by motor vehicle 110 consistent with thediscussion herein.

In one embodiment, imaging system 112 provides captured image data toevent intelligence analyzer 116, which extracts one or more eventinformation elements from the sign by performing image analysis on thecaptured sign's image. In embodiments, the image analysis performed byevent intelligence analyzer 116 can include applying one or more machinelearning model trained image classifiers to the captured image of thesign to extract and recognize, for example, event information elementssuch as the listing agent's name, a company associated with the sign, alogo displayed on the sign, determine that the directional indicator ispresent on the sign, etc. Furthermore, the positioning system 114 maydetermine a real world location of the motor vehicle 110 when an imageof the sign 150 was captured in order to associate the determined realworld location of motor vehicle 110 with the image of the sign, and thusthe extracted information. Similarly, timing information associated withwhen the image was captured may be associated by event intelligenceanalyzer 116 with the extracted information.

In one embodiment, event intelligence analyzer 116 may further processone or more of the extracted event information elements to better definethe element, such as coordinating the determined location with thedirectional indicator to predict a real world location of an event. Forexample, motor vehicle's 110 determined position and heading are (x₀,y₀, z₀) and true-North, and thus the extracted directional indicator ofthe sign may indicate that the location of the even advertised by sign150 is at (x₁, y₁, z₁) plus or minus a predefined confidence interval.In another example, the extracted sign's purpose (e.g., real estatelisting) and the extracted address and/or listing agent's name, may beused by event intelligence analyzer 116 to obtain data not listed on thesign. Event intelligence analyzer 116 may query a third party server140, such as a multiple listing server (MLS) databased system, based onthe address and/or listing agent's name to complete informationassociated with the sign, such as price of a house associated with thereal estate listing, time of the event, etc. Event intelligence analyzer116 may further infer one or more additional event information elements,for example, based on the time associated with the capture of image dataof the sign 150. For example, based on the time of day, and informationextracted from the sign (e.g., sign's purpose), event intelligenceanalyzer 116 can infer whether an event is still ongoing, how long theevent may last, etc. Such inferences may be based on one more machinelearning processes performed by event intelligence analyzer 116 (e.g.,learning that yard sales typically end by 3 PM on Sundays), based onsearches of third party server(s) 140 for hours defined for an event(e.g., a store's hours are 8 AM to 10 PM), based on social norms (e.g.,a lunch special will only be valid during typical lunch hours of 11 AMto 2 PM), based on data associated with known categories (e.g., realestate open houses are typically only on the day in which a sign isfirst seen, and for a limited time), etc.

In embodiments, event intelligence analyzer 116 of motor vehicle 110communicates the data associated with and extracted from the capturedimage of the sign, such as the estimated location of the sign, acategorization of the sign's type, an estimated location of an eventadvertised in the sign including an optional confidence interval, a timeof the image capture, various information elements extracted from thesign's content (e.g., addresses, time, directional indicators, businessnames, individual names, words of event description, etc.), as well asinformation learned based on the extracted information (e.g., byquerying one or more third party server(s) 140), to event aggregationserver 130.

In one embodiment, event aggregation server 130 is a remote computerprocessing system that may receive event information elements extractedby event intelligence analyzer 116 of motor vehicle 110 from image data(e.g., the data generated by motor vehicle 110 from the image, GNSS dataassociated with sign 150, and information learned by querying thirdparty system(s) 140). Event intelligence analyzer 116 of server 130 mayalso receive one or more of image, time, and location data from motorvehicle 110, and perform its own event information extraction using anevent intelligence analyzer 116. In yet another embodiment, eventintelligence analyzers 116 of server 130 and motor vehicle 110 maycooperatively perform event information extraction, such as by applyingdifferent image analysis classifier to a captured image of sign 150. Inone embodiment, event aggregation server 130 may receive image datacaptured of sign 150, time data when the image was captured, andlocation data associated with motor vehicle 110 where the image wascaptured. In this embodiment, event aggregation server 130 uses its ownevent intelligence analyzer 116 to extract the various event informationelements discussed above. In another embodiment, both motor vehicle 110and event aggregation server 130 may both attempt to extract the sameinformation elements, different event information elements, or refineinformation associated with the same information element. For example,event intelligence analyzer 116 of motor vehicle may infer, based on itsown analysis that an event's duration should not last longer than 3 PM.However, information elements extracted for the event by other imagedata captured by the same or other motor vehicles, and in someembodiments from different signs at different locations for the sameevent, may be used by event intelligence analyzer 116 of eventaggregation server 130 to refine event information elements (e.g., eventduration confidence, location approximation, etc.)

In the embodiments, event aggregation server 130 then maps extractedsign information elements to a real world location to build an eventprofile associated with the sign 150 in an events profile database. Inembodiments, the event profiles database maintained by event aggregationserver 130 includes a unique record for each determined event, and eachof the information elements associated with the event. For example,event aggregation server 130 stores a record of the first instanceassociated with the capture and extraction of event details from sign150. Then, when a new instance of event details (e.g., subsequentlyuploaded to or extracted by server 130) is received for sign 150, forexample from a second motor vehicle (not shown) that also captured animage and extracts information associated with sign 150, a new record ofthe event is not created by event aggregation server 130. Instead, anyadditional information received from subsequent image capture and eventinformation extraction may be integrated into the existing record byevent aggregation server 130 to further refine, expand, or update theevent's profile. For example, if timing information is not available foran event (e.g., is not extractable from the sign, not available fromquerying a third party server 140, cannot be inferred from a societal orbusiness norm, etc.), the event may be given a default duration (e.g., 2hours from creation of the event profile). Then, when a new capture ofthe sign is uploaded to event aggregation server 130 from a second motorvehicle, event aggregation server may extend the event's duration, forexample by a predefined amount of time such as extending the event'sduration by an additional 1 hour. Furthermore, multiple captures of thesame and/or different signs for the same event may be utilized by eventaggregation server 130 to adjust and/or maintain an event's informationelements. For example, one or more confidence values, such as confidenceassociated with an event's inferred duration, freshness of eventinformation elements, etc. can be adjusted as new instances of the sameevent are detected, or no additional instance of the event are detected.Other techniques may be utilized by the event aggregation server 130 tocomplete and maintain an event's information details in an associatedevent profile record. For example, event aggregation server 130 mayquery one or more wireless network traffic indication services todetermine a number of concurrent unique wireless network accessesrelative to the location of the event. When the number of concurrentunique accesses exceeds a threshold, the event may be determined tostill be ongoing, and the event's duration in the event profile can beextended. Various techniques for determining event duration, such asreceipt of multiple instances of the metadata associated with imagecaptured of sign 150, searching for event duration on one or more thirdparty server(s) 140, performing access density analysis for wirelessnetwork access points proximate to an event, enabling event organizersto set event durations at event aggregation server, edit eventdurations, end events, based on crowdsourced application data (e.g.,social media check-ins at an event, photographic uploads of an event),based on crowd sourced navigation data (e.g., based on a number ofnavigation services used to the same location), etc., may be used byeven aggregation server 130.

Furthermore, event aggregation server 130 may apply its own imageanalysis (e.g., machine learning based event classifiers) to extractadditional event details and/or verify the received informationassociated with sign 150. For example, event aggregation server 130 mayapply a different image classifier to recognize logos displayed on sign150, may apply optical character recognition to the sign and then applya text analysis classifier to extract information elements, as well asother image analysis techniques. Furthermore, event aggregation server130 may use the received and/or extracted information to queryadditional third party server(s) 140, such as using a logo as the basisfor an image based search of a business associated with the sign 150.

In embodiments, in addition to preventing duplicate event records of thesame event in an event profiles database, and optionally contributingadditional information to event records, event aggregation server 130further establishes a boundary around the event. For example, theboundary may be a geofence established around the determined location ofthe event. As discussed in greater detail herein, the geofence may bemaintained around the event for the duration of the event, so thatadditional motor vehicles and/or user devices, such as motor vehicle 120with a positioning system 124 can be informed of relevant events basedon the timeliness of the event, proximity of motor vehicle 120 to theevent, and relevance of the event to a user. Furthermore, differentboundary dimensions may be used for different types of events. Forexample, a boundary having a first set of dimensions may be establishedaround a non-commercial event (e.g., a boundary with a ¼ mile radius isestablished around a garage sale), whereas a boundary having a secondset of dimensions is established around commercial events (e.g., aboundary having a 1 mile radius is established around a restaurant witha lunch special).

In one embodiment, the event aggregation server 130 may use boundariesto merge and/or maintain a distinction between different events. Forexample, two boundaries may be set around the same real world location,or may be set at different real world locations but intersect oneanother. For example, if there are more than one event at the samelocation, such as a plant sale and a car wash, the events may beseparated and different boundaries maintained by event aggregationserver 130 based on the differences in the type of event. If, however,it is determined by event aggregation server 130 that the events are thesame, such as a multi-part event having the same name, events having thesame address, etc., the different boundaries and events may be merged.

In one embodiment, event aggregation server 130 is further responsiblefor establishing user profiles associated with the users of various userdevices (e.g., motor vehicle 110 and 120). For example, eventaggregation server 130 generates user profiles by receiving from a usera specification of event categories for which notifications should beprovided (e.g., real estate, home wares sales, restaurants, etc.). Inembodiments, a user may establish, update, and maintain a user profileat event aggregation server 130 via an interface of motor vehicle,mobile device (e.g., mobile telephone), or other computing device. Eventaggregation server 130 may additionally receive details orcharacteristics associated with each category specified by user, such asa geographic area of interest (e.g., a neighborhood or city for realestate, a company selling home wares, a type of cuisine, a time at whichnotifications should be received, etc.), subjects of interest (e.g.,real estate, restaurant, retail, garage sales, etc.), a time associatedwith various interests (e.g., real estate events on weekends, restaurantevents between 5 PM and 8 PM, etc.), event characteristics (e.g., realestate listings in a certain price range, type of foods offered byrestaurants, neighborhoods having garage sales, etc.), as well as otherinformation. The event notification categories and notificationcharacteristics are then used by event aggregation server 130 tomaintain user profile records for distribution of relevant eventnotifications to users.

In one embodiment, after a user establishes a user profile with eventaggregation server 130, the user's mobile device (e.g., motor vehicle120) then receives relevant event notifications based on, for example,the motor vehicle's reported location, one or more event characteristicsin the user's profile, and whether an event is still active. Therefore,the event notifications are relevant to a user's interests, timelyrelative to an event's duration, and relevant to a user's currentlocation. For example, motor vehicle 120 may report its location asdetermined by location system 124 to event aggregation server 130. Then,based on the motor vehicle's 130 current location and a user profileassociated with the user of vehicle 120, ongoing events in an event'sprofile data store can be queried based on the user's profile, location,and time. When a relevant event is found, event aggregation server 130further determines whether the event is still ongoing and whether themotor vehicle's current location is within a predefined boundarysurrounding the event (e.g., has the user breached a geofence associatedwith an event). A relevant, local, and timely event notification maythen be sent to motor vehicle 120, including information relevant to theevent (e.g., location, event details, time of event, geographiccoordinates associated with the event, a confidence that the event isstill ongoing, etc.). The motor vehicle 120 may then act on thenotification, such as navigating to the event. For autonomous vehicles,the event notification may be used to re-route the vehicle toautomatically navigate to the event by configuring a navigation systembased on the received event details. For semi-autonomous ornon-autonomous vehicles, the event notification may be used to configurea navigation system the can prompt the user with directions to theevent.

Beneficially, motor vehicle 120 may receive event information detailsfor events listed by sign 150, which are not actually witnessed by animaging system (not shown) of motor vehicle 120 or a user of motorvehicle 120. In fact, motor vehicle 120 may not come into any visualcontact with sign 150, but may be alerted to the event advertised by thesign based on various characteristics predefined by the user (e.g., realestate listings around location X, for single family homes below theprice of Y). Not only is such an event notification beneficial to theuser of motor vehicle 120, but it is also beneficial to event organizersby opening up the event to a wider range of interested parties.

Although motor vehicles are discussed above (e.g., motor vehicle 110 and120), the event information capture, detail extraction, and notificationcan be carried out by any combination of mobile entities, such as mobiletelephones, smart glasses, wearable devices, drone systems, motorvehicles, or other mobile devices and systems that are capable ofperforming the image capture, image analysis, and positing functionsdiscussed herein. In the embodiments discussed herein, motor vehicles,mobile entities, mobile devices, mobile systems, etc. areinterchangeable when referring to the systems that can be used toexecute the processes and techniques discussed herein.

FIG. 2 is block diagram of one embodiment of a system 200 including amotor vehicle and an event aggregation server. Motor vehicle 202 andevent aggregation server provide additional details for motor vehicle110 and event aggregation server 130 discussed above in FIG. 1.

In one embodiment, motor vehicle 202 is a system, which may include oneor more processor(s) 212, a memory 205, a network interface 204, awireless subsystem 205, a display 206, a navigation system 218, and animaging system 212. It should be appreciated that motor vehicle 202 mayalso include, although not illustrated, one or more user and/or hardwareinterfaces, one or more power device(s) (e.g., vehicle battery,autonomous drive control system, etc.), a propulsion system (e.g. anelectric, gasoline, etc. powered motor), a steering system, a brakingsystem, as well as other components typically associated with motorvehicles. Although only a single wireless subsystem 215 is illustrated,it is understood that network interface 204 may be capable ofcommunicatively coupling autonomous vehicle 202 to any number ofwireless subsystems (e.g., Bluetooth, Wi-Fi, Cellular, or othernetworks) to transmit and receive data streams through a wireless linkto/from event aggregation server 250.

In one embodiment, event aggregation server 250 is also a system, whichmay include one or more processor(s) 252, memory 260, and wirelesssubsystem 254. It should be appreciated that event aggregation server250 may also include, although not illustrated, a user interface (e.g.,keyboard, touch-screen, or similar devices), a power device (e.g., abattery), a display screen (e.g., an LCD display), as well as othercomponents typically associated with computer processing systems.

In embodiments, the memories (e.g., memory 205 and memory 260) of motorvehicle 202 and event aggregation server 250 may be coupled toprocessor(s) to store instructions for execution by the processors, suchas processor(s) 212 and processor(s) 252. In some embodiments, thememory is non-transitory, and may store one or more processing modules.In one embodiment, memory 205 of motor vehicle 202 may store one or moreprocessing modules of event intelligence system 220, such as imageanalyzer 222, user interface generator 226, event aggregation serverinterface (I/F) 228, 3rd party system I/F 230 to implement embodimentsdescribed herein.

Furthermore, memory 260 of event aggregation server 250 may also includean event aggregator 270 including an event mapper 272, event profilegenerator 274, user profile generator 276, image analyzer 290, and eventnotification engine 276.

It should be appreciated that the embodiments as will be hereinafterdescribed may be implemented through the execution of instructions, forexample as stored in memory or other element, by processor(s) and/orother circuitry of motor vehicle 202 and event aggregation server 250.Particularly, circuitry of motor vehicle 202 and event aggregationserver 250, including but not limited to processor(s) 212 andprocessor(s) 252 may operate under the control of a program, routine, orthe execution of instructions to execute methods or processes inaccordance with the aspects and features described herein. For example,such a program may be implemented in firmware or software (e.g. storedin memory 205 and/or memory 260) and may be implemented by processors,such as processor(s) 212 and processor(s) 252, and/or other circuitry.Further, it should be appreciated that the terms processor,microprocessor, circuitry, controller, etc., may refer to any type oflogic or circuitry capable of executing logic, commands, instructions,software, firmware, functionality and the like.

Further, it should be appreciated that some or all of the functions,engines, or modules described herein may be performed by motor vehicle202 itself and/or some or all of the functions, engines or modulesdescribed herein may be performed by another system connected throughnetwork interface 204 to motor vehicle 202. Thus, some and/or all of thefunctions may be performed by another system, and the results orintermediate calculations may be transferred back to motor vehicle 202.In some embodiments, such other device may comprise a server, such asevent aggregation server 250 and/or another server (not shown).

In one embodiment, motor vehicle 202 includes an imaging system 212,which can include one or more cameras for capturing images of theenvironment surrounding motor vehicle 202. For example, one or morecameras of imaging system 212 may capture images of objects surroundingmotor vehicle 202 as motor vehicle travels between real world locations.Motor vehicle also includes a positioning system 214, such as a GNSSbased positioning system that determines a current real world locationof the motor vehicle, in real time, as the motor vehicle 202 travelsbetween real world locations. Both the captured images and locationinformation are continuously or periodically provided to eventintelligence system 220.

Event intelligence system 220 includes image analyzer 222. Imageanalyzer 222 is responsible for determining and extracting variousinformational characteristics about signs, such as ephemeral signboardsdiscussed in greater detail above, that are depicted within the imagescaptured by imaging system 212. In embodiments, image analyzer 222accesses one or more classifiers 224, for example by accessing theclassifiers when stored in memory 205). Each classifier may be a machinelearning trained image analysis classifier that extracts data fromvisual objects within the captured images, and performs one or morerecognition operations for determining the content and/or meaningassociated with the extracted data. For example, one of the classifiers224 may include a text recognition classier trained to recognize varioustypes of written data (e.g., handwritten, mechanically reproduced,etc.). As another example, one of the classifiers 224 may include animage recognition classifier trained to recognize business logos. As yetanother example, one of the classifiers 224 may include an imagerecognition classier trained to recognize directional indicators (e.g.,arrows, line, and other markings) and, as discussed in greater detailherein, infer a real world location of an event from the directionalindicator and the location of the motor vehicle when the image wascaptured. As yet another example, one of the classifiers 224 mayassociate various extracted content with an inferred purpose or meaningfor the sing's content, such as distinguishing between real estate signs(e.g., when real estate logos are recognized, MLS listing IDs are found,etc.), retail store signs (e.g., based on content advertising “sale”),restaurant signs (e.g., with content indicative of food, or food relatedcontent such as “Happy Hour!”). As yet another example, limitersassociated with the sign may also be extracted by one or moreclassifiers to recognize explicitly stated event duration (e.g., “3-4only!”) and based on societal norms (e.g., “Happy Hour!” specialstypically run from 4 PM to 6 PM). Classifiers 224 may include any numberof classifiers for extracting and recognizing the content that maypotentially be depicted in images captured of signs. In embodiments, theextracted information is information to be associated with an event forwhich the sign is advertising, such as a real estate listing, acommercial sale, a restaurant special, a yard sale, or any other type ofevent advertised by an ephemeral sign. Furthermore, in embodiments, thelocation of the event and the location of the sign may be different(e.g., the event may be at a first real world location a distance awayfrom the sign placed at a second real world location).

In one embodiment, one or more of the extracted informationalcharacteristics extracted from a sign, such as textual content,graphical content, etc. is provided to 3^(rd) party system I/F 230.3^(rd) party system I/F 230 utilizes the extracted information to queryone or more 3^(rd) party systems for additional information relevant toan event advertised by a sign. For example, real estate systems (e.g.,MLS listing server, commercial real estate company, etc.) may be queriedwhen the information extracted from a sign are indicative of a realestate event, such as utilizing an extracted real estate agent name froma sign to query an MLS listing service for listings associated with theagent's name. As another example, a merchant's website may be queriedwhen information extracted from a sign indicates that the merchant ishosting an event at one of their real world stores. Any obtained 3^(rd)party system information is provided by 3^(rd) party system I/F 230 toimage analyzer 222.

Image analyzer 222 then transmits event information obtained from themotor vehicle's captured images of signs, using event aggregation serverI/F 228, to the event aggregation server 250. In one embodiment, theinformation sent by image analyzer 222 includes the extracted eventinformation elements and associated meanings of those elements, anyadditional 3^(rd) party system event information elements, a location ofthe motor vehicle where an image of a sign was captured, and a time whenthe image was captured (e.g., the sign was observed by motor vehicle202). Additional information, such as the captured image itself, anyinferences generated by image analyzer (e.g., an inferred societal norm,a predicted location based on the motor vehicles location and adirectional indicator, etc.), an identifier associated with the motorvehicle 202 or a user of the motor vehicle 202, may also be transmittedto the event aggregation server 250.

Event aggregator 270 of event aggregation server 250 receives the datafrom motor vehicle 202 for generating and/or refining an event profileassociated with the event advertised by the ephemeral sign. In oneembodiment, for the first instance of a captured image of a sign for anevent, as determined from sign content, event information, inferred signlocation, etc., event profile generator 274 generates a uniquelyidentified event profile in event data store 280. That is, event profilegenerator 274 creates a single event profile for each event for whichsign information is captured, regardless of whether different motorvehicles capture information from the same event sign or whetherdifferent signs for the same event are captured. Furthermore, thevarious event informational elements received from motor vehicle (e.g.,inferred event location, title of event, event type, recited duration ifany, etc.) are stored in the record containing the event profile.

In one embodiment, event aggregator 270 also includes an image analyzer290 (e.g., similar to image analyzer 222) that may perform its own imageanalysis using the same or different classifiers. For example, imageanalyzer 290 may apply more computationally intensive image classifiersthan those employed by image analyzer 222, so that event aggregationserver 270 can perform different or additional image informationextraction that may not be feasible on the more limited computationalresources of the motor vehicle. In another embodiment, however, eventaggregation server 250 may only receive an image from motor vehicle 202,a location of motor vehicle 202 when the image was captured, and a timewhen the image was captured. In this embodiment, image analyzer 290 mayperform the sign information extraction discussed above. In yet anotherembodiment, event aggregator 270 does not employ its own image analyzerwhen received event information is sufficient to create an event profile(e.g., contains a certain subset of data, such as duration, title, eventtype, etc.).

In any of the embodiments discussed above, event mapper 272 of eventaggregator 270 maps a real world location (e.g., address, coordinates,etc.) to an event profile. The real world location may be a locationinferred from event intelligence analyzer 220 of motor vehicle 202(e.g., based on the motor vehicles position and a sign's directionalindicator, based on a 3^(rd) party system's listing for an event asdetermined by a 3^(rd) party query performed by motor vehicle, etc.), aswell as based on a location determination of event aggregator 270. Inembodiments, the mapped real world location enables the event profilefor the event to be associated with the actual location of the event,even when the sign (e.g., from which the event information wasextracted) is not located proximate or near the actual event.Furthermore, the mapping of the event to a real world location enablesevent profile generator 274 to avoid creating duplicate event profilerecords (e.g., records for the same event) from information extractedfrom signs at different locations, but which advertise the same event.Finally, the mapping and the event information elements enable eventprofile generator 274 to maintain different events for the same realworld location (e.g., a restaurant with a “Taco Tuesday” event which isactive all day on Tuesday, and a “Happy Hour” event that is activeMonday through Thursday from 4 PM to 6 PM). In one embodiment, themapping of a real world location to an event further enables eventprofile generator 274 to establish one or more boundaries around anevent, such as geofence(s) discussed above, to be associated with anevent in the event's profile.

In one embodiment, event profile generator 274 further infers an eventduration or active status for each event maintained in event data store280. As discussed herein, the event duration can be inferred from thecontent of the sign, the capture of images of sign(s) for the same eventat different time by the same and/or different motor vehicles, based oninformation obtained from 3^(rd) party systems, etc. Furthermore, asdiscussed herein, wireless network access point information can bequeried by event profile generator 274 to infer an event is still activebased on a number of devices that access a wireless network within apredefined area surrounding an event. Other information may alsoinfluence an event's duration, such as assigning an event a defaultduration when other sources are unable to provide an even duration, andextending the event's default duration each time a successive image ofan event sign is captured.

Event aggregator server 250, as discussed above, maintains unique eventprofiles for events advertised by ephemeral and non-ephemeral signs.Furthermore, the event profiles are updated and maintained by eventaggregation server 250 in real time so that the event informationobtainable by event signs is current and fresh. Additionally, eventinformation captured by the same or multiple users can inform eventaggregator server 250 as to the same or different event details, as wellas confirming or extending event durations.

In one embodiment, event aggregator 270 further maintains a user profiledata store 282. User profile generator 276 may interact with userinterface generator 226 of motor vehicle 202 in the creation of a userprofile. Other devices, such as a user's mobile telephone, personalcomputer, tablet, etc. may also be used to establish a user profilemaintained by event aggregation server. User profile generator 276establishes a user profile for a user including various interests,notification preferences, geographical regions, etc. For example, a userprofile could specify an interest in real estate listings, a real estatetype (e.g., condo, house, commercial property, etc.), a price range forlistings the user is interested in, a specific neighborhood, etc. Asanother example, a user may specify an interest in restaurant specials,their preferred cuisine types, level of discount (e.g., buy one get one,10% off or greater, etc.), time of day (dinner specials, breakfastspecials on weekends, etc.), etc.

In one embodiment, event aggregation server I/F 228 of motor vehicle 202periodically sends event notification engine 276 of event aggregationserver 250 a current location of the motor vehicle 202. The currentlocation is a location determined by positioning system 212. In oneembodiment, positioning system 214 can generate the motor vehiclescurrent position 202 specifically for reporting to the eventnotification engine 276. In another embodiment, positions determinedwhile motor vehicle is performing another function (e.g. navigationusing navigation system 218) may also be transmitted to evennotification engine 276.

In one embodiment, a user identifier (e.g., an identifier associatedwith the user's profile in user profile data store 282) is alsotransmitted with the current location of the motor vehicle. Eventnotification engine 276 utilizes the user identifier to access a userprofile, and determine based on user interests specified in the userprofile, if the motor vehicle's current location is within a geofence ofany relevant event. When event notification engine 276 determines thatthe motor vehicle has breached a geofence to a relevant event (e.g., onein which user profile attributes match event profile attributes), and aduration of the event indicates that the event is still active, eventnotification engine 276 sends a notification to motor vehicle. Inembodiments, the event notification includes one or more of the relevantattributes about the event, such as event category, location, estimatedduration, distance to event, etc.

User interface generator 226 of event intelligence system generates auser interface based on the received event notification, and displaysthe user interface using display 206. The user interface can includeuser selectable elements to, for example, request additional eventinformation, program navigation system 218 with an event's location,etc. Thus, the display generated by user interface generator 226 enablesa user to browse event notifications, and select to navigate to anevent. For example, in an autonomous vehicle, an event notification canautomatically or with permission of a user drive a user to a locationwhere an event is occurring.

As discussed herein, event notifications are generated for motor vehicle202 based on the motor vehicle's 202 current location, attributesassociated with an event, and a profile of a user of the motor vehicle202. That is, the user and/or motor vehicle need not see a signadvertising the event in order to receive the event notification.Beneficially, users of motor vehicles can be informed of events forwhich they might be interested regardless of whether they see an eventnotification or the event itself. Furthermore, the event details may besourced from a plurality of different motor vehicle capturing imagesfrom the same or different event signs, applying the same or differentimage analysis classifiers, etc. so that a single robust, accurate, andcurrent profile of the event can be created and maintained. Furthermore,duration information can be updated using subsequent sign image capture,wireless network usage statistics, etc. to ensure that events are stillactive, so that event notifications generated by event aggregator arestill relevant.

FIG. 3 is a flow diagram of one embodiment of a method 300 forcapturing, collecting, and distributing event information displayed onsign. The method 300 is performed by processing logic that may comprisehardware (circuitry, dedicated logic, etc.), software (such as is run ona general purpose computer system or a dedicated machine), firmware, ora combination. In one embodiment, the method 300 is performed by amobile device (e.g., motor vehicle 102 or 202).

Referring to FIG. 3, processing logic begins by capturing, by the mobiledevice, an image of a sign that displays information for an event(processing block 302). As discussed herein, processing logic capturesimages of the objects surrounding mobile device, such as while a motorvehicle travels between real world locations. However, other systems,such as smart glasses, mobile telephones, wearable devices with imagingcapabilities, etc., may also capture images of objects during use.Furthermore, the images are captured by an imaging system of the mobiledevice, such as one or more cameras, a RADAR system, a LIDAR system,etc.

Processing logic then extracts information for the event from thecaptured image of the sign (processing block 304). In one embodiment,processing logic may apply one or more trained machine learning imageanalysis classifiers to the captured image data to extract variousinformational attributes from the sign depicted in the image data, andwhich describe the event. For example, the classifiers can extractinformation from the sign's content depicted in the captured image, suchas textual information indicating names associated with an event, acompany associated with an event, a category of an event (e.g., realestate, restaurant, garage sale, etc.) etc. As another example, aclassifier may extract and analyze an image of a sign, such as corporatelogos. As yet another example, directional indicators such as arrowsindicative a location relative to a sign where an event is located, mayalso be extracted from an image of a sign. As another example, theinformation extracted from one or more classifiers can ingested by otherclassifiers to infer additional information for an event, such asinferring one or more societal norms or contextual meanings fromextracted textual content (e.g., “happy hour” refers to a restaurant/barevent usually occurring from 4 PM to 6 PM, a “garage sale” category ofsigns usually refers to an event happening on a weekend from 8 AM to 3PM, a “lunch special” sign refers to a time period surrounding 12 noon,etc.).

Processing logic then determines a location of the mobile device whenthe image of the sign was captured (processing block 306). As discussedherein, the location of the mobile device may be obtained using a GNNSbased positioning system of the mobile device. Processing logic thenuploads, to an event aggregation server, (i) a time when the image wascaptured, (ii) the information for the event extracted from the capturedimage, and (iii) a location of the event determined from extracted eventinformation, a location of the signboard, or a combination thereof(processing block 308). The information uploaded to the eventaggregation server may include additional information, such as thecaptured image itself to enable the event aggregation server to performits own image analysis, as discussed herein. Furthermore, as discussedherein, the uploading of the information extracted from the sign, thelocation, and the time, enable event profiles to be created, maintained,updated, and distributed to and from a number of different mobiledevices.

FIG. 4 is a flow diagram of one embodiment of a method 400 forcapturing, collecting, and distributing event information displayed onsign. The method 400 is performed by processing logic that may comprisehardware (circuitry, dedicated logic, etc.), software (such as is run ona general purpose computer system or a dedicated machine), firmware, ora combination. In one embodiment, the method 400 is performed by asystem, such as the system 100 or 200 having a mobile device (e.g.,motor vehicle 102 or 202) and an event aggregation server (e.g., eventaggregation server 130 or 250).

Referring to FIG. 4, processing logic of the mobile device begins bycapturing an image of a sign (processing block 402). In embodiments,images are captured continuously or periodically by the mobile device.For example, where mobile device is a motor vehicle, a forward facingcamera used by the motor vehicle for navigation purposes maycontinuously capture images as the motor vehicle navigates between realworld locations. The images capture the environment outside of the motorvehicle, and may include the capture of one or more signs (e.g.,temporary and non-temporary signs advertising various types of events).As discussed herein, processing logic performs an image analysis on thecaptured image(s) to extract sign information (processing block 404).For example, processing logic can apply one or more machine learningtrained image analysis classifier to extract and/or infer a number ofinformational attributes about the event being advertised in the sign,such as event type, event location, duration of event, etc. Processinglogic then transmits a location of the mobile device where the image wascaptured, a time when the mobile device captured the image, and one ormore of the extracted information elements and the captured image to anevent aggregation server (processing block 406).

Processing logic of the event aggregation server receives theinformation associated with a sign from the mobile device (e.g., thetime, the location, the extracted information and/or the image)(processing block 408). The processing logic of the event aggregationserver may then optionally perform its own analysis to extract signinformation (processing block 410). In embodiments, processing logic ofthe event aggregation server performs image analysis to determineadditional information associated with an event being advertised by asign, to apply different image analysis classifiers, to find missinginformation, to confirm information provided by mobile device, to expandthe information provided by the mobile device, to determine eventinformation when only an image is provided by processing logic, etc.

Processing logic of the event aggregation server then maps the extractedsign information to a real world location (processing block 412). Asdiscussed herein, the mapping can be based upon the sign's own content(e.g., an extracted address), as a result of querying a third partysystem (e.g., using a real estate agent's name, a restaurant's name, aninferred location, etc. to 3^(rd) party listing, corporate or directoryservice), by inference (e.g., based upon the mobile device's locationwhen an image was captured and a directional indicator), etc.Furthermore, in embodiments, an interface may be provided by eventaggregation server (not shown) that enables event organizers to add,revise, and update information associated with their events, such assetting an event active status, event duration, as well as other factorsassociated with an event. Processing logic utilizes the extractedinformation and the mapped location to create/update an event profilerecord in a data store (processing block 414). As discussed herein, theevent profile is unique to each event, and thus processing logic assignsa unique event identifier to the event in the data store. Furthermore,additional information from the mobile device, as well as from othermobile device attributable to the event, is added to the unique eventprofile record (e.g., multiple records are not established for the sameevent).

Processing logic of the mobile device further establishes a user profilewith the event aggregation server (processing block 418), which eventaggregation server uses to create/update a user profile in a data store(processing block 416). In embodiments, a user of the mobile device mayset up the profile on an interface of the mobile device, such as byselecting various event notification preferences (e.g., event type,times of notifications, characteristics of an event, etc.). The profilemay be associated with a user, so that even if an operator of a motorvehicle changes, event notifications subsequently sent to the motorvehicle will be relevant to the vehicle's current operator.

Processing logic of the mobile device then periodically communicates acurrent location and a user ID to the event aggregation server(processing block 420). The processing logic of the event aggregationserver uses the user ID to query an event profile associated with theuser based on the user's current location (processing block 422). Thisquery enables processing logic of the event aggregation server todetermine when an event is currently ongoing for which the user may beinterested (e.g., overlap of profile interest attributes with eventattributes), and for which the user is a threshold distance from theevent (e.g., within a geofence established around the event). The eventlocated by the event aggregation server, however, is not necessarily anevent for which the mobile device is currently, or has ever, seen anevent sign. That is, the user of mobile device may be notified ofrelevant and ongoing events that have been sourced by other users, butfor which the user of mobile device is near.

When the conditions for a notification are satisfied, processing logicof the event aggregation server notifies the mobile device of the eventincluding event details and a location of the event (processing block424). The processing logic of the mobile device then provides ordisplays one or more of the event details from the notification to theuser (processing block 426). In embodiments, different subsets of theevent details provided by event aggregation server may be provided touser. For example, an initial notification may provide or display afirst set of details, such as an event category, host of an event, etc.Then, upon a user request for additional information, processing logicprovides or displays additional information, such as distance from theevent, duration of the event, reviews from 3 ^(rd) party review systemsassociated with the event, etc.

In one embodiment, the notification sent by event aggregation server atprocessing block 424 included the location of the event. In oneembodiment, processing logic of the mobile device may utilize thislocation to navigate a user to the event (processing block 428). Forexample, where mobile device is an autonomous motor vehicle, the eventlocation may be used by the autonomous motor vehicle to automaticallyreroute the vehicle to the event, upon a user selection to do so. Asanother example, a turn by turn navigation system may be programmedusing the location in the notification to prompt a user with directionsto the event.

It should be appreciated that the devices (e.g., motor vehicles,autonomous motor vehicles, cellular phones, server computer systems,etc.) discussed herein may communicate via one or more wirelesscommunication links through a wireless network that are based on orotherwise support any suitable wireless communication technology. Forexample, one or more of the devices may associate with a networkincluding a wireless network. In some aspects the network may comprise alocal area network or a wide area network. Furthermore, the devicesvehicle may support or otherwise use one or more of a variety ofwireless communication technologies, protocols, or standards such as,for example, CDMA, TDMA, OFDM, OFDMA, WiMAX, and Wi-Fi.

Those of skill in the art would understand that information and signalsmay be represented using any of a variety of different technologies andtechniques. For example, data, instructions, commands, information,signals, bits, symbols, and chips that may be referenced throughout theabove description may be represented by voltages, currents,electromagnetic waves, magnetic fields or particles, optical fields orparticles, or any combination thereof.

Those of skill would further appreciate that the various illustrativelogical blocks, modules, circuits, and algorithm steps described inconnection with the embodiments disclosed herein may be implemented aselectronic hardware, computer software, or combinations of both. Toclearly illustrate this interchangeability of hardware and software,various illustrative components, blocks, modules, circuits, and stepshave been described above generally in terms of their functionality.Whether such functionality is implemented as hardware or softwaredepends upon the particular application and design constraints imposedon the overall system. Skilled artisans may implement the describedfunctionality in varying ways for each particular application, but suchimplementation decisions should not be interpreted as causing adeparture from the scope of the present disclosure.

The various illustrative logical blocks, modules, and circuits describedin connection with the embodiments disclosed herein may be implementedor performed with a general purpose processor, a digital signalprocessor (DSP), an application specific integrated circuit (ASIC), afield programmable gate array (FPGA) or other programmable logic device,discrete gate or transistor logic, discrete hardware components, or anycombination thereof designed to perform the functions described herein.A general purpose processor may be a microprocessor, but in thealternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

The steps of a method or algorithm described in connection with theembodiments disclosed herein may be embodied directly in hardware, in asoftware module executed by a processor, or in a combination of the two.A software module may reside in RAM memory, flash memory, ROM memory,EPROM memory, EEPROM memory, registers, hard disk, a removable disk, aCD-ROM, or any other form of storage medium known in the art. Anexemplary storage medium is coupled to the processor such the processorcan read information from, and write information to, the storage medium.In the alternative, the storage medium may be integral to the processor.The processor and the storage medium may reside in an ASIC. The ASIC mayreside in a user terminal. In the alternative, the processor and thestorage medium may reside as discrete components in a user terminal.

In one or more exemplary embodiments, the functions described may beimplemented in hardware, software, firmware, or any combination thereof.If implemented in software as a computer program product, the functionsmay be stored on or transmitted over as one or more instructions or codeon a non-transitory computer-readable medium. Computer-readable mediacan include both computer storage media and communication mediaincluding any medium that facilitates transfer of a computer programfrom one place to another. A storage media may be any available mediathat can be accessed by a computer. By way of example, and notlimitation, such non-transitory computer-readable media can compriseRAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic diskstorage or other magnetic storage devices, or any other medium that canbe used to carry or store desired program code in the form ofinstructions or data structures and that can be accessed by a computer.Also, any connection is properly termed a computer-readable medium. Forexample, if the software is transmitted from a web site, server, orother remote source using a coaxial cable, fiber optic cable, twistedpair, digital subscriber line (DSL), or wireless technologies such asinfrared, radio, and microwave, then the coaxial cable, fiber opticcable, twisted pair, DSL, or wireless technologies such as infrared,radio, and microwave are included in the definition of medium. Disk anddisc, as used herein, includes compact disc (CD), laser disc, opticaldisc, digital versatile disc (DVD), floppy disk and blu-ray disc wheredisks usually reproduce data magnetically, while discs reproduce dataoptically with lasers. Combinations of the above should also be includedwithin the scope of non-transitory computer-readable media.

The previous description of the disclosed embodiments is provided toenable any person skilled in the art to make or use the methods,systems, and apparatus of the present disclosure. Various modificationsto these embodiments will be readily apparent to those skilled in theart, and the generic principles defined herein may be applied to otherembodiments without departing from the spirit or scope of thedisclosure. Thus, the present disclosure is not intended to be limitedto the embodiments shown herein but is to be accorded the widest scopeconsistent with the principles and novel features disclosed herein.

What is claimed is:
 1. A method for capturing, collecting, and distributing event information displayed on signs, the method comprising: capturing, by a mobile device, an image of a sign that displays information for an event; extracting information for the event from the captured image of the sign; determining a location of the mobile device when the image of the sign was captured; and uploading, to a server, (i) a time when the image was captured, (ii) the information for the event extracted from the captured image, (iii) a location of the event determined from extracted event information, (iv) a location of the sign, or a combination thereof.
 2. The method of claim 1, wherein extracting information for the event from the captured image comprises: performing an image analysis comprising analyzing the captured image with one or more classifiers to detect one or more objects within the image, the one or more objects comprising graphical information associated with the event.
 3. The method of claim 1, wherein extracting information for the event from the captured image comprises: performing optical character recognition on the captured image to extract textual information associated with the information for the event.
 4. The method of claim 1, wherein extracting information for the event from the captured image comprises: detecting a directional indicator on the sign based on an image analysis; and estimating the location of the event based on an estimated location of the sign and the directional indicator, wherein the estimated location of the sign is based on the location of the mobile device when the image of the sign was captured.
 5. The method of claim 1, wherein extracting information for the event from the captured image comprises: querying a database for additional information for the event based on textual information extracted from the image, one or more objects detected within the image, or a combination thereof; and integrating the additional information, received from the database in response to the query, with information known about the event.
 6. The method of claim 1, wherein the time, the information, and the location uploaded to the server establish an event profile record for the event in an events profile database maintained by the server, the event profile record comprising an event identifier, a duration of the event based at least in part on the time, a geofence associated with a predefined boundary surrounding the event based at least in part on the location, and data indicative of the event based at least in part on the information.
 7. The method of claim 1, wherein the mobile device comprises a motor vehicle.
 8. A mobile device for capturing, collecting, and distributing event information displayed on signs, the mobile device comprising: an imaging system to capture an image of a sign that displays information for an event; a memory configured to store the captured image; and one or more processors communicably coupled with the memory and the imaging system, the one or more processors configured to: extract information for the event from the captured image of the sign, and determine a location of the mobile device when the image of the sign was captured; and a communications subsystem communicably coupled with the one or more processors to upload to a server, (i) a time when the image was captured, (ii) the information for the event extracted from the captured image, (iii) a location of the event determined from extracted event information, (iv) a location of the sign, or a combination thereof.
 9. The mobile device of claim 8, wherein the one or more processors are further configured to perform an image analysis comprising analyzing the captured image with one or more classifiers to detect one or more objects within the image, the one or more objects comprising graphical information associated with the event.
 10. The mobile device of claim 8, wherein the one or more processors are further configured to perform optical character recognition on the captured image to extract textual information associated with the information for the event.
 11. The mobile device of claim 8, wherein the one or more processors are further configured to: detect a directional indicator on the sign based on the performed image analysis; and estimate the location of the event based on an estimated location of the sign and the directional indicator, wherein the estimated location of the sign is based on the location of the mobile device when the image of the sign was captured.
 12. The mobile device of claim 8, wherein the one or more processors are further configured to: query a database for additional information for the event based on textual information extracted from the image, one or more objects detected within the image, or a combination thereof; and integrate the additional information, received from the database in response to the query, with information known about the event.
 13. The mobile device of claim 8, wherein the time, the information, and the location uploaded to the server establish an event profile record for the event in an events profile database maintained by the server, the event profile record comprising an event identifier, a duration of the event based at least in part on the time, a geofence associated with a predefined boundary surrounding the event based at least in part on the location, and data indicative of the event based at least in part on the information.
 14. The mobile of claim 8, wherein the mobile device comprises a motor vehicle.
 15. A non-transitory computer readable storage medium including instructions that, when executed by one or more processors, cause the one or more processors to perform operations for capturing, collecting, and distributing event information displayed on signs, the operations comprising: capturing an image of a sign that displays information for an event; extracting information for the event from the captured image of the sign; determining a location of a mobile device when the image of the sign was captured; and uploading, to a server, (i) a time when the image was captured, (ii) the information for the event extracted from the captured image, (iii) a location of the event determined from extracted event information, (iv) a location of the sign, or a combination thereof.
 16. The non-transitory computer readable storage medium of claim 15, wherein the time, the information, and the location uploaded to the server establish an event profile record for the event in an events profile database maintained by the server, the event profile record comprising an event identifier, a duration of the event based at least in part on the time, a geofence associated with a predefined boundary surrounding the event based at least in part on the location, and data indicative of the event based at least in part on the information.
 17. An apparatus, comprising: means for capturing an image of a sign that displays information for an event; means for extracting information for the event from the captured image of the sign; means for determining a location of a mobile device when the image of the sign was captured; and means for uploading, to a server, (i) a time when the image was captured, (ii) the information for the event extracted from the captured image, (iii) a location of the event determined from extracted event information, (iv) a location of the sign, or a combination thereof.
 18. The apparatus of claim 17, wherein the time, the information, and the location uploaded to the server establish an event profile record for the event in an events profile database maintained by the server, the event profile record comprising an event identifier, a duration of the event based at least in part on the time, a geofence associated with a predefined boundary surrounding the event based at least in part on the location, and data indicative of the event based at least in part on the information.
 19. A method for distribution of event information displayed on signs, the method comprising: establishing a user profile with a server, wherein the user profile comprises one or more interests of a user of a mobile device; reporting a current location of the mobile device to the server; receiving an event notification for an event, wherein the event notification is selected and delivered by the server to the mobile device based, at least in part, on: (i) the current location of the mobile device indicating that a geofence established by the server around the event has been breached by the current location of the mobile device, (ii) the one or more interests of the user in the user profile, and (iii) a duration associated with the event indicating that the event is active; and wherein the event is an event established by the server in response to receiving event information for the event captured by a second mobile device from a sign that displays information for the event.
 20. The method of claim 19, further comprising: utilizing, by the mobile device, a location of the event in the event notification to configure a navigation system of the mobile device to navigate the user to the event.
 21. The method of claim 19, further comprising: displaying one or more attributes associated with the event to the user in response to receipt of the event notification for the event by the mobile device.
 22. The method of claim 19, wherein a sign for the event is not within a field of view of an imaging system of the mobile device.
 23. The method of claim 19, wherein a location of the event and a time of the event are estimated based, at least in part, on a time and a location of the second mobile device when an image of the sign was captured by the second mobile device.
 24. A mobile device, comprising: a positioning system to determine a current location of the mobile device; a communications subsystem communicably coupled with the positioning system to report the current location of the mobile device to a server; and one or more processors communicably coupled with the communications subsystem to: establish with a server using the communication system, a user profile that comprises one or more interests of a user of the mobile device, and provide an event notification, received by the communication subsystem, to the user of the mobile device, wherein the event notification is selected and delivered by the server to the mobile device based, at least in part, on: (i) the current location of the mobile device indicating that a geofence established by the server around the event has been breached by the current location of the mobile device, (ii) the one or more interests of the user in the user profile, and (iii) a duration associated with the event indicating that the event is active, and wherein the event is an event established by the server in response to receiving event information for the event captured by a second mobile device from a sign that displays information for the event.
 25. The mobile device of claim 24, further comprising: a navigation system, wherein the one or more processors are configured to utilize a location of the event in the event notification to configure the navigation system to navigate the user to the event.
 26. The mobile device of claim 24, further comprising: a display configured to render a graphic user interface generated by the one or more processors, wherein the graphical user interface displays one or more attributes associated with the event in response to receipt of the event notification for the event.
 27. The mobile device of claim 24, wherein a sign for the event is not within a field of view of an imaging system of the mobile device.
 28. The mobile device of claim 24, wherein a location of the event and a time of the event are estimated based, at least in part, on a time and a location of the second mobile device when an image of the sign was captured by the second mobile device.
 29. A mobile system, comprising: means for establishing a user profile with a server, wherein the user profile comprises one or more interests of a user of the mobile system; means for reporting a current location of the mobile system to the server; means for receiving an event notification for an event, wherein the event notification is selected and delivered by the server to the mobile system based, at least in part, on: (i) the current location of the mobile system indicating that a geofence established by the server around the event has been breached by the current location of the mobile system, (ii) the one or more interests of the user in the user profile, and (iii) a duration associated with the event indicating that the event is active; and wherein the event is an event established by the server in response to receiving event information for the event captured by a mobile device from a sign that displays information for the event.
 30. A non-transitory computer readable storage medium including instructions that, when executed by one or more processors, cause the one or more processors to perform operations for distribution of event information, the operations comprising: establishing a user profile with a server, wherein the user profile comprises one or more interests of a user of a mobile device; reporting a current location of the mobile device to the server; receiving an event notification for an event, wherein the event notification is selected and delivered by the server to the mobile device based, at least in part, on: (i) the current location of the mobile device indicating that a geofence established by the server around the event has been breached by the current location of the mobile device, (ii) the one or more interests of the user in the user profile, and (iii) a duration associated with the event indicating that the event is active; and wherein the event is an event established by the server in response to receiving event information for the event captured by a second mobile device from a sign that displays information for the event. 